Sorry - above post should have said turned debugging ON not OFF
Thanks. I appreciate the offer but this project has developed into a high value proprietary system which we would not be comfortable releasing.
For now, in the production copy, I have just commented out the "Welcome" notification call and will continue to investigate.
One thing that would aid in the debugging is how do I have the debugger and log file look at my downloaded copy of the boilerplate and module-zero on my disk drive rather than
D:\Halil\Github\aspnetboilerplate\src\Abp.EntityFramework\EntityFramework\AbpDbContext.cs:line 214
Thanks again Terry
Thanks! I upgraded to Abp 1.2.1 and the issue disappeared
Sorry I should have checked this. It is the second line (_appNotifier.WelcomeToTheApplicationAsync(user)) that is causing the timeout. If I comment it out the user is added correctly but if I uncomment it fails.
the second line (SubscribeToAllAvailableNotificationsAsync) is NOT a problem whether it is commented or not.
Hi - the problem was occurring with a basic login (not impersonation). It also happened on all browsers I tried.
I found a few more differences in files between what I had and the new version of the Abp and was able to resolve the anti-forgery token error.
Everything seems to now be working.
Thanks... Terry
Sorry - I solve the problem. Never fails that I spend hours trying to resolve the issue myself and then as soon as I post I see the problem.
In this case, I forgot to enter the [DependsOn( typeof(AbpZeroOwinModule),... in the WebModule class
Still having an issue with the following entries in the Log file but will need to work through that (unless someone know the answer)
WARN 2016-12-29 16:15:14,416 [25 ] ity.AntiForgery.AbpMvcAntiForgeryManager - The provided anti-forgery token was meant for a different claims-based user than the current user. WARN 2016-12-29 16:15:14,578 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Empty or invalid anti forgery header token. WARN 2016-12-29 16:15:14,748 [25 ] rity.AntiForgery.AbpAntiForgeryApiFilter - Requested URI: <a class="postlink" href="http://localhost:6234/api/services/app/session/GetCurrentLoginInformation">http://localhost:6234/api/services/app/ ... nformation</a>
I'm also encountering very strange behavior with the abp.timing.convertToUserTimezone in the abp.moment.js (which is the one that is getting executed) I set the user time zone to Pacific time I pass in the current local time using Date.now() which is 1469464471941 momentDate._d : Mon Jul 25 2016 13:34:31 GMT-0300 (Atlantic Daylight Time) - this is correct and the targetDate returned : Mon Jul 25 2016 06:34:31 GMT-0300 (Atlantic Daylight Time) -not correct
The targetDate should be Mon Jul 25 2016 09:34:31 GMT-0700 (Pacific Daylight Time)
There are two errors here. It has not first set the time to UTC before converting it to Pacific so it is out by 3 hours and it has left the "GMT -0300 (Atlantic Daylight Time)"
Was able to solve the problem. I published the web application to another local workstation and discovered that the "compilation" entry that I added to web.config to fix the first error resulted in a duplicate compilation entry (which was causing the 500 error on Azure) . I fixed this error and everything worked!
I thought I may have missed one or more files in the "include in project" so I published the application to a file system and copied the published file structure to another workstation. I installed the application from scratch and was surprised that it worked right away. Obviously it is not missing files.
Problem solved. The AppNavigationProvider.cs class was in the /App_Start/Navigation folder and when I made the changes to add the new features it looks like this class changed folders (?) Anyway, I had not moved my copy of the class to the /App/Startup and so it was using your copy. As soon as I replaced your copy with my copy, all was good.
Thanks... Terry
